Skip to content

docs: match proxy error text on connection errors - #6572

Merged
danieltprice merged 4 commits into
mainfrom
polly/connect-errors-proxy-text-20261109
Nov 17, 2026
Merged

danieltprice merged 4 commits into
mainfrom
polly/connect-errors-proxy-text-20261109

Conversation

@bgrenon

@bgrenon bgrenon commented Nov 9, 2026

Copy link
Copy Markdown
Collaborator

LKB-20979

The connection errors page quoted the endpoint ID error with different wording than Neon returns, and it left out the extra guidance Neon adds to the unsupported startup parameter errors. This makes both match what users see.

Changes

content/docs/connect/connection-errors.md

Endpoint ID error. Before:

ERROR: The endpoint ID is not specified. Either upgrade the Postgres client library (libpq) for SNI support or pass the endpoint ID (the first part of the domain name) as a parameter: '&options=endpoint%3D'. See https://neon.com/sni for more information.

After:

ERROR: Endpoint ID is not specified. Either please upgrade the postgres client library (libpq) for SNI support or pass the endpoint ID (first part of the domain name) as a parameter: '?options=endpoint%3D'. See more at https://neon.tech/sni

Unsupported startup parameter. Both variations now have a note that the message ends with:

Please use unpooled connection or remove this parameter from the startup package. More details: https://neon.tech/docs/connect/connection-errors#unsupported-startup-parameter

How this was checked

The new text is the message Neon's pooler sends, copied word for word, so people who search for the exact error text find this page. The options parameter starts with ?, and the old text had & and had dropped the <endpoint-id> placeholder.

I did not run a live test. Triggering these errors needs a specific client setup, which a SQL session can't reproduce.

Changed files

File Change
content/docs/connect/connection-errors.md Correct the endpoint ID error text and note the suffix on the startup parameter errors

Not auto-merged. Awaiting your review.

This pull request and its description were written by Isaac.

LKB-20979

Co-authored-by: Isaac <no-reply@databricks.com>
@vercel

vercel Bot commented Nov 9, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
neon-next Ready Ready Preview Nov 17, 2026 8:52pm UTC

Request Review

Co-authored-by: Isaac <no-reply@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
@danieltprice

Copy link
Copy Markdown
Collaborator

Live test results

Both errors were triggered live against a throwaway Neon project (psql 18.6).

# Check Result
1 Endpoint ID error (sslsni=0, no channel_binding) 🔧 Wording matched; URL is https://neon.com/sni, not neon.tech. Fixed in 455075b
2 Unsupported startup parameter (pooled, options=-c statement_timeout=1000) 🔧 Suffix matched; URL is https://neon.com/docs/..., not neon.tech. Fixed in 455075b

Also in this PR:

  • Merged main to fix a failing Vercel preview on the week-old base.
  • next.config.js: /sni now redirects to /docs/connect/connection-errors#the-endpoint-id-is-not-specified instead of the top of the page. Verified on the preview deployment.

@danieltprice
danieltprice marked this pull request as ready for review November 17, 2026 20:56
@danieltprice
danieltprice merged commit 5601591 into main Nov 17, 2026
5 checks passed
@danieltprice
danieltprice deleted the polly/connect-errors-proxy-text-20261109 branch November 17, 2026 20:58

This branch was successfully deployed

1 active deployment
Preview – neon-next — 9cf87b40 Deployed Nov 17, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants